home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
ftp.cs.arizona.edu
/
ftp.cs.arizona.edu.tar
/
ftp.cs.arizona.edu
/
icon
/
newsgrp
/
group95b.txt
/
000044_icon-group-sender _Fri Jun 16 10:30:07 1995.msg
< prev
next >
Wrap
Internet Message Format
|
1995-09-18
|
2KB
Received: by cheltenham.cs.arizona.edu; Fri, 16 Jun 1995 12:29:48 MST
To: icon-group@cs.arizona.edu
Date: 16 Jun 1995 10:30:07 -0700
From: dave@cs.arizona.edu (Dave Schaumann)
Message-Id: <3rsf2v$1e@lectura.CS.Arizona.EDU>
Organization: University of Arizona CS Department, Tucson AZ
Sender: icon-group-request@cs.arizona.edu
References: <3rpcmd$ie0@canopus.cc.umanitoba.ca>, <3rqsq6$g9s@lectura.CS.Arizona.EDU>
Subject: Language features & behavior of &null (was Re: ICON vs Ted Nelson)
Errors-To: icon-group-errors@cs.arizona.edu
In article <3rqsq6$g9s@lectura.CS.Arizona.EDU>,
Scott E Gilbert <scott@CS.Arizona.EDU> wrote:
>
>Ok, so lets spark up a thread of our own. What are your least and most
>favorite features about Icon? What would you change?
Mostly what I don't like about Icon is some important (IMHO) things
are missing. Most obviously, some general interface to system calls
would make Icon much more useful for programming in shell-script
situations. Also, it would be nice if Icon had some facility for
writing large programs (ie, name space control, inline functions,
enumerated types, real booleans, etc).
>Personally, I'd like to see the &null value act as a general purpose
>identity for all of the operators except when used as a procedure call.
I disagree. IMHO, this is one place where Icon got it right. One of
my pet peeves is when some obscure default of a language hides an error
I've made by leaving something out. If I've forgotton to initialize
a variable, I want to know it.
-Dave